docs/start/config.json (1)

44-47: Optional: Consider renaming “Environment Functions” to “Isomorphic Utilities”

Since the PR description questions the naming, “Isomorphic Utilities” (or “Environment-aware Utilities”) may better convey the intent without implying only functions. If you prefer this, we should update both the page titles and these nav labels together.

Also applies to: 129-132

docs/start/framework/react/environment-functions.md (9)

10-15: Grammar: “Start provides”

Subject-verb agreement and light copy tweaks.

-Start provide three core environment functions:
+Start provides three core environment functions:

---

45-48: Grammar: “a no-op” and punctuation

Clarify the client behavior phrasing.

-// ℹ️ On the **client**, it is no-op (returns `undefined`)
+// ℹ️ On the **client**, it is a no-op (returns `undefined`).

---

59-62: Grammar: “a no-op” and punctuation

Same tweak for the server-side note.

-// ℹ️ On the **server**, it is no-op (returns `undefined`)
+// ℹ️ On the **server**, it is a no-op (returns `undefined`).

---

73-75: Grammar: “a no-op” and punctuation

Apply the same phrasing/punctuation for consistency.

-// ℹ️ On both **client** and **server**, it is no-op (returns `undefined`)
+// ℹ️ On both **client** and **server**, it is a no-op (returns `undefined`).

---

88-91: Fix heading: backticks and casing

Current “## envOnly Functions” renders oddly. Prefer plain language.

-## `env`Only Functions
+## Environment-only Functions

---

117-123: Tree-shaking section: wording and clarity

Minor grammar improvements and clearer phrasing.

-Environment functions are tree-shaken based on the environment for each bundle produced.
+Environment functions are tree-shaken per environment for each produced bundle.

-Functions created using `createIsomorphicFn()` are tree-shaken. All codes inside `.client()` are not included in server bundle, and vice-versa.
+Functions created using `createIsomorphicFn()` are tree-shaken. All code inside `.client()` is excluded from the server bundle, and vice versa.

-On the server, implementation of `clientOnly` functions are replaced with a function that throws an `Error`. The reverse is true for `serverOnly` functions on the client.
+In the server bundle, `clientOnly` implementations are replaced with a function that throws an `Error`. The reverse is true for `serverOnly` functions in the client bundle.

---

79-85: TS typing for no-op example

If we want to be explicit for TypeScript users, “void” is the idiomatic return type for a no-op (you can still note that it evaluates to undefined at runtime).

-// basic no-op implementation
-function noop() {}
+// basic no-op implementation (TypeScript)
+const noop: () => void = () => {}

---

99-112: Avoid locking docs to exact error message strings

The quoted error texts might diverge from implementation over time. Suggest describing the behavior generically or quoting less rigidly (e.g., “throws an error on the client/server”).

Would you like me to replace the exact strings with a generic description, or verify the current runtime messages in the codebase to keep them accurate?

---

1-4: Optional: Page title naming

If you decide to rename the nav label (e.g., to “Isomorphic Utilities”), mirror it here for consistency.

-title: Environment Functions
+title: Isomorphic Utilities

docs/start/framework/solid/environment-functions.md (1)

1-4: Consider adding a capitalized replacement and validate scope

If the source doc contains “React” (capitalized) or other proper nouns, also add a case-sensitive replacement to ensure titles and prose read naturally for Solid. Example:

 ---
 ref: docs/start/framework/react/environment-functions.md
-replace: { 'react': 'solid' }
+replace:
+  {
+    'react': 'solid',
+    'React': 'Solid'
+  }
 ---

Also, confirm the replacement mechanism applies to code blocks as intended (e.g., it should convert @tanstack/react-start to @tanstack/solid-start without affecting unrelated identifiers).

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.